home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20010306-20010921
/
000068_news@columbia.edu _Sat Apr 21 15:03:18 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2001-09-20
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by uhaligani.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id PAA10793
for <kermit.misc@cpunix.cc.columbia.edu>; Sat, 21 Apr 2001 15:03:18 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id OAA04539
for kermit.misc@watsun.cc.columbia.edu; Sat, 21 Apr 2001 14:48:34 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: telnet file transfer
Date: 21 Apr 2001 18:48:33 GMT
Organization: Columbia University
Message-ID: <9bskm1$4dp$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <3AE1B392.CCF45BA9@informatik.uni-erlangen.de>,
Stefan Meinlschmidt <meinlschmidt@informatik.uni-erlangen.de> wrote:
: > Better use scp, that's the whole goal of scp ;-)
: > scp /path/to/local_file
: > loginname@ip.of.remote.computer:/path/to/destination
:
: Fully agree, provided that you have it. I have a machine here with ssh
: but with a broken scp. If you don't have ssh (and rsh/rcp) at all, you
: can still pipe your data through a telnet session.
:
Again, it's not *all* you can do. Kermit is a Telnet client that can
transfer files over its own Telnet connection:
http://www.columbia.edu/kermit/
This answers the original poster's question about how to transfer a file
over a Telnet connection.
Such questions always quickly veer off-topic when answered by "don't use
Telnet, use ssh or scp", but let's not be too quick to condemn trusty old
FTP and Telnet. First of all, they are not *inherently* insecure. Secure
versions of both are available:
http://www.columbia.edu/kermit/telnetd.html
as well as secure clients.
Second, these secure versions of Telnet and FTP use reliable, standard,
and manageable security methods such as Kerberos 4 and 5, SSL/TSL, and
SRP, rather than SSH, which has some rather serious flaws and risks that
everybody likes to overlook, simply because SSH is easy to install.
It's not far off the mark to say the "easier" the security method, the
greater the risks.
Third, Telnet continues to offer many convenience features not found in
the alternatives, via its extensive and fully standardized negotiation
and in-band command mechanism.
- Frank